I understand that NBVH cannot be used in combinationi with SSL in order
to perform the initial SSL handshake. However, does this really prevent
me from defining NBVH for use at later stages in apache processing? For
example, let's assume I want two NBVH with two different FQDNs, on the
same IP, using port 443 - and I want both to use the same server
certificate, but I want them to use different other settings
(DocumentRoot, logging settings, etc.).
I would imagine the main problem in this case was making sure that the
single server certificate is compatible with both FQDNs, but assuming
that can be arranged via wildcards - will this work? Does anyone know of
any limitations to this (for example, things that definitely cannot work
this way)?
style=3D'font-size:10.0pt;
font-family:Arial'>I understand that NBVH cannot be used in
class=3DSpellE>combinationi
with SSL in order to perform the initial SSL handshake. However, does =
this
really prevent me from defining NBVH for use at later stages in apache
processing? For example, let’s assume I want two NBVH with two =
different
class=3DSpellE>FQDNs, on the same IP, using port 443 – and =
I want
both to use the same server certificate, but I want them to use =
different other
settings (DocumentRoot, logging settings,
etc…).
style=3D'font-size:10.0pt;
font-family:Arial'>
style=3D'font-size:10.0pt;
font-family:Arial'>I would imagine the main problem in this case was =
making
sure that the single server certificate is compatible with both
class=3DSpellE>FQDNs, but assuming that can be arranged via =
wildcards
– will this work? Does anyone know of any limitations to this (for
example, things that definitely cannot work this =
way)?
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org